Problem Note 52108: The IBM WebSphere, Oracle WebLogic, and JBoss web application servers might have degraded response time or they do not respond at all
 |  |  |  |  |
When you export a report from SAS Web Report Studio, deadlocked threads might occur in your web application server. Accumulation of deadlocked threads eventually compromises the web application server's ability to respond. For example, when deadlocked threads accumulate, you might notice a degradation of response time. In addition, as the thread pool is consumed, the server becomes unable to respond at all, which leads to an outage.
IBM WebSphere and Oracle WebLogic both detect thread deadlocks, and they report the problem in their respective application-server logs. However, JBoss does not have the capability to detect deadlocks. For all three web application servers, you can determine whether threads are deadlocked by performing a thread dump, as described in SAS KB0036230, "Instructions for creating a Java thread dump."
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Web Report Studio | Linux for x64 | 4.31_M2 | 4.4_M1 | 9.4 TS1M1 | |
| Solaris for x64 | 4.31_M2 | 4.4_M1 | 9.4 TS1M1 | |||
| HP-UX IPF | 4.31_M2 | 4.4_M1 | 9.4 TS1M1 | |||
| 64-bit Enabled Solaris | 4.31_M2 | 4.4_M1 | 9.4 TS1M1 | |||
| 64-bit Enabled AIX | 4.31_M2 | 4.4_M1 | 9.4 TS1M1 | |||
| Microsoft® Windows® for x64 | 4.31_M2 | 4.4_M1 | 9.4 TS1M1 | |||
| z/OS | 4.31_M2 | 4.4_M1 | 9.4 TS1M1 | |||